(233/330) 1538 - Sidekick 1.2 does not remember my parser

Matthieu, this could be due to the bug in the plugin you were working on (new javascript sidekick). I cannot reproduce it. However I see that the manually selected parser is lost after buffer switching.

Here is the code that introduces the problem. Maybe Dale could check if it can be safely removed?

18729 daleanson //{{{ handleBufferChange() method
18729 daleanson @EBHandler
18729 daleanson public void handleBufferChange(BufferChanging bmsg) {
18729 daleanson buffer = bmsg.getBuffer();
18729 daleanson buffer.setProperty(SideKickPlugin.PARSER_PROPERTY, null);
18729 daleanson } //}}}

- **summary**: Sidekick 1.2 do not remember my parser --> Sidekick 1.2 does not remember my parser
- **assigned_to**: nobody --> daleanson
- **priority**: 8 --> 6

It's actually damien's patch which introduced this bug, so I am assigning to him.

- **assigned_to**: daleanson --> kog13

Introduced by patch 3081956

my previous comment was incorrect, the patch was not responsible but a line added by dale.
ok, I will try removing the buffer.setMode(xxx, null) and start testing sidekick with that.

- **assigned_to**: kog13 --> ezust

nuts, its more complicated than that. Assigning back to dale.

- **assigned_to**: ezust --> daleanson

Committed 21843 which seems to work for me.

- **assigned_to**: daleanson --> ezust
- **status**: open --> pending-fixed